Migrating and upgrading users can revise their yard model when they are finished with installation and are ready to review the yard configuration.
Installation instructions are highlighted here so that you can understand the implications. For example, if your database has containers positioned in LANE exchange areas, N4 puts those containers into the Lost Containers view in the XPS GUI (Container 
Lost & Found Lost Containers) if the default position naming format (B1C2) does not match what you were using in your previous version of N4. Once you correct the position naming convention as noted below, you can restart XPS, and the containers that were in Lost & Found display in their correct locations in the G-type blocks.
There are two approaches you can take to revise the yard model to make the User Label Format, Internal Label Format, and bin name tables consistent with position naming your operation:
Specify your yard in Yard Editor, or
Specify it in the decompiled yard file (as you did with previous N4 versions).
Prerequisites:
Before you can use the Yard Editor feature in N4 4.0.13, you must import an image map of your yard (on page 1).
If you are an upgrading user, and your yard has not changed from your previous version, you do not need to upload an image map unless and until you need to edit the yard. However, until you import an image map of your yard, you will not have access to the visual features that central to Yard Editor.
Review Tips for migrating and upgrading with Yard Editor (on page 1).
To specify your yard in Yard Editor:
With XPS and the Bridge daemon shut down, clone the active yard in the Yard Models view.
Open Yard Editor and import the yard.nyd file for the active yard model.
In the Yard Models view, open the cloned yard model and review and edit the bin name tables. This also includes editing the default bin name tables created for and assigned to converted LANE blocks.
The default assignments use the following conventions:
N4 creates a stack block with one section for each lane. It derives the number of lanes from the difference between the ingress and egress values that were in the backed up database (originally from the SPARCS Settings.txt file).
In the position label formats, lanes equate to the column positions.
N4 creates a bin name table for each lane (column) starting with the name '1000' and incrementing by one for each lane. For example, if there were three lanes specified for the LANE logical block for the earlier version of N4, N4 4.0.13 creates bin name table 1000 for the first lane, 1001 for the second lane, and 1002 for the third lane.
The default position label format is B1C2: One letter for the block, two letters for the column.
For example, in an earlier version of N4, a LANE position of 100.1 (block 100 and lane 1) would by default in N4 2.2 be 101.1. Using 'B1C2.T1' for the User Label Format, in the Names tab of the Yard Editor's Stack Block form, this would be block 100, column (lane) 01, and tier 1.
Open the Yard Editor for the cloned yard, import an image of your yard, and set at least two reference points with latitudinal/longitudinal coordinates.
Draw the perimeter around the clone.
Place the existing stack and non-stack blocks, taking care to accurately anchor them on the image according to the following conventions:
For a stack block: Click the anchor point for the lower left corner of the block.
For a non-stack block or track plan: Click the map for the first anchor point; drag the pointer and click each anchor point of the block or track plan; double-click to finalize the outline.
For a berth: Click the map and, without releasing the mouse button, drag the pointer up and left or down and right to create the berth outline; release the mouse button to finalize the outline.
Make sure the label format and column names for the straddle blocks match the lane names of Yard Exchange Lanes in the Gate form. See Review Gate Lanes with converted straddle grid blocks (on page 1) for more information.
Apply the changes to the active yard.
Start up the Bridge daemon and XPS, and view the yard in XPS to verify that it is accurately configured.
To specify your yard in the decompiled yard file:
Start up N4 against a backed up database instance.
Start the Bridge daemon and XPS.
Initialize and then shut down XPS.
Copy the yard.nyd file that N4 wrote to the data folder in XPS.
Start up a solo XPS client. See Set up a solo workstation in your installation guide.
Decompile the yard.nyd file to create a yard source file (yard.txt). See Decompile a yard file in your installation guide.
Edit the yard source file as you would have with an earlier version of N4.
Notice that in yard source files for versions 2.2 and above, the #LOG BLOCK section is at the end, and instead of a LANE logical block, there is a stack block of type G.
Recompile the yard file. See Compile the yard source file in your installation guide.
In the Yard Editor view of an inactive yard model, import the compiled yard file. See Import a Compiled Yard File (on page 1).